Hi Steven
KFLOP was designed to perform real-time tasks and relieve the PC/Windows/Mach3 from requiring to be real-time. This is a big change from how Mach3 was originally designed to function and from how long time Mach3 users expect things to work. Basically everything low level and real-time is performed and configured in KFLOP such as Step/Dir Generation, Limits, Soft Limits, Homing, Probing, MPG, Jogging, encoder feedback, Threading, Backlash Compensation, Hardware feed hold, etc. Mach3 still performs the high-level functions like the GUI, GCode interpreter, Trajectory Planning, requests the Home Sequences, requests a Probe
operation, etc...
Soft Limits are configured in KFLOP and trigger a Hardware FeedHold when tripped. They are set in encoder counts and are usually set after Homing when the machine coordinates have been established.
HTH Regards TK
Group: DynoMotion |
Message: 8162 |
From: karmannelectric |
Date: 8/25/2013 |
Subject: Re: Mach and Soft Limits |
Thanks! I'm not sure if it's how I set up my machine, or what. When I use the jog keys in Mach, my machine doesn't move for short key presses. Because it moves so fast, it's tricky to hold an arrow key down long enough to get it to move, but not so long that I crash into the side... Has anyone else considered adding jog buttons directly to the kflop/kanalog? Any suggestions how to do this and still have mach know the real position?
Also, I like how Mach slows down a per-defined distance before hitting the soft limit. Do you think this would be hard to implement in kflop?
I'm looking forward to writing my own probing routines... for some reason I can't get my accurate renishaw probe to work accurately with mach. I'm using a scope and it's likely to be vibration but Mach triggers, stops, and then when the vibrations settle down, the probe isn't triggered anymore. Since I have little to no control on how Mach works, I'm hoping to move past the trigger point a bit, then back off until the probe is not triggered anymore.
Thanks again,
- Steve
--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Steven
>
>
> KFLOP was designed to perform real-time tasks and relieve the PC/Windows/Mach3 from requiring to be real-time. This is a big change from how Mach3 was originally designed to function and from how long time Mach3 users expect things to work. Basically everything low level and real-time is performed and configured in KFLOP such as Step/Dir Generation, Limits, Soft Limits, Homing, Probing, MPG, Jogging, encoder feedback, Threading, Backlash Compensation, Hardware feed hold, etc. Mach3 still performs the high-level functions like the GUI, GCode interpreter, Trajectory Planning, requests the Home Sequences, requests a Probe operation, etc...
>
> Soft Limits are configured in KFLOP and trigger a Hardware FeedHold when tripped. They are set in encoder counts and are usually set after Homing when the machine coordinates have been established.
>
> HTH
> Regards
> TK
>
>
>
> ________________________________
> From: karmannelectric <steve@...>
> To: DynoMotion@yahoogroups.com
> Sent: Sunday, August 25, 2013 10:42 AM
> Subject: [DynoMotion] Mach and Soft Limits
>
>
>
> Â
> I finally got around to figuring out soft limits using Mach and a smooth stepper, and wish I would have done sooner. The latest machine I'm setting up, using a kflop and kanalog, I'm initially going to run Mach 3 on it and am trying to set up soft limits again. It appears from reading the archives that in the Mach/kflop combo, soft limits don't work on the Mach side, just the kflop side? If true, (or even if not) could someone post a quick overview of how Mach and the kflop interact? Maybe that will help my understanding if I understood which "brain" can do which function...
>
> Thanks for kflop! It's a steep(ish) learning curve, especially after coming from a decade or more of Mach experience, but the support is MUCH better for the kflop, and the kflop is much more powerful/flexible!
>
> Steven Ciciora
>
|
|
Group: DynoMotion |
Message: 8163 |
From: Tom Kerekes |
Date: 8/25/2013 |
Subject: Re: Mach and Soft Limits |
Hi Steve,
Your Jogging issue may be due to excessively low Jerk. Very low Jerk has the effect of taking a long time to begin accelerating and then consequently a long time to start decelerating. KFLOP's Acceleration and Jerk settings are used for continuous jogging.
MPGs and Jog Buttons can be connected directly to KFLOP to get guaranteed response, but the Keyboard Jogging should be very responsive 99.9% of the time so check the above settings to see if that is the main issue.
I can't think of an easy way to implement a slow down region.
Regarding probing: for G31 Mach3 just sets up a single motion which we stop by firing hardware Feedhold. But you could do something like you describe with a Mach3 Macro or a KFLOP C Program.
Regards TK
| | | |